The version number must be bump in separate occasions:
- when releasing a BLEAD-FINAL (or anything besides a BLEAD-POINT),
  bump the version at the beginning of the release process
- after releasing a BLEAD-POINT, bump the version to prepare for
  the next dev release (even it the next release is likely to be
  an RC or BLEAD-FINAL)
- after releasing a BLEAD-FINAL, bump the version to the new .0
  for the new dev cycle

- make the perlpolicy update more prominent by adding a specific section
  header
- clarify the PERL_API constants instructions and make them release-specific
- move the end-of-support email instructions to the email section

Co-authored-by: Eric Herman <eric@freesa.org>